Say the current numbers, and stop claiming the GUI never sees a key - #22
Merged
Conversation
An audit of every page against the source it describes. The install line still fetched v0.3.8. The library is at v0.12.0, so the one line a new reader copies out of the site gave them something months old. It appears on the homepage and on Getting Started. The homepage claimed 135k/s event ingest. The site's own performance page says ~149k/s at 100,000 events and ~170k/s at 20,000, so the headline number matched neither of its own rows. Plaza's frame table was stale in both columns. The budgets in scripts/frame-budget.sh are 600, 2200 and 150 microseconds; the page said 400, 1500 and 200, which also overstated the patch budget. The p90 column now matches the app's README. The prose said a live feed, which is not what the harness does: it seeds a fixed 240-note feed into a store of its own so a run means the same thing twice. And 63 widget nodes was measured before the row grew; a long feed mounts around 460. "The GUI never sees the key" was false, in the same way and for the same reason as the line corrected in zig-nostr/notary#66: the setup screen has an nsec field and posts the secret to the daemon on import. Supported operations listed five methods where nip46.Method has seven, and described the approval policy as a per-request allowlist without mentioning that an answer carries a duration, which is the part that decides whether a signing loop becomes a prompt loop. Smaller: a place is not "a milestone away" from private messages (two), Plaza reads nine kind:0 keys rather than eight, and three NIP rows are half written rather than none. The places panel picture is the re-render from zig-nostr/plaza#299, so the image and its caption agree again.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An audit of every page against the source it describes.
The install line still fetched
v0.3.8. The library is atv0.12.0, so the one line a new reader copies out of the site gave them something months old. It appears on the homepage and on Getting Started.The homepage claimed 135k/s event ingest. The site's own performance page says ~149k/s at 100,000 events and ~170k/s at 20,000, so the headline number matched neither of its own rows.
Plaza's frame table was stale in both columns. The budgets in
scripts/frame-budget.share 600, 2200 and 150 microseconds; the page said 400, 1500 and 200, which also overstated the patch budget. The p90 column now matches the app's README. The prose said a "live feed", which is not what the harness does: it seeds a fixed 240-note feed into a store of its own so a run means the same thing twice. And "63 widget nodes" was measured before the row grew; a long feed mounts around 460."The GUI never sees the key" was false, in the same way and for the same reason as the line corrected in zig-nostr/notary#66: the setup screen has an nsec field and posts the secret to the daemon on import. Supported operations listed five methods where
nip46.Methodhas seven, and described the approval policy as a per-request allowlist without mentioning that an answer carries a duration, which is the part that decides whether a signing loop becomes a prompt loop.Smaller: private messages are two milestones out rather than one, Plaza reads nine kind:0 keys rather than eight, and three NIP rows are half written rather than none.
The places panel picture is the re-render from zig-nostr/plaza#299, so the image and its caption agree again.
Not touched:
/notary/panel-request.jpgstill shows Approve/Deny where the app now draws four buttons with the asker and a preview. Its alt text stays as it is until the picture is retaken, because fixing the caption alone would make the mismatch worse.